Uav authentication method and system

ABSTRACT

An authentication method includes sending, by a device of an unmanned aerial vehicle (UAV), a device identification (ID) of the device and a randomly generated random number to an authentication apparatus of the UAV; receiving, by the device from the authentication apparatus, an encrypted session key and an encrypted random number that are obtained by the authentication apparatus based on the device identification; decrypting, by the device according to a device key of the device, the encrypted session key and the encrypted random number to obtain decrypted session key and decrypted random number, respectively; and determining, by the device, whether an authentication of the authentication apparatus is passed based on the randomly generated random number and the decrypted random number.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of application Ser. No. 16/003,799, filed on Jun. 8, 2018, which is a continuation application of International Application No. PCT/CN2015/097046, filed on Dec. 10, 2015, the entire contents of both of which are incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates to unmanned aerial vehicle (UAV) security technology and, more particularly, to a UAV authentication method and system.

BACKGROUND

An unmanned aerial vehicle (UAV) is an unmanned aircraft controlled by a radio remote control device and a programming control device of the UAV. Currently, when the UAV is powered up or reset, components of the UAV are started without authentication. When a component of the UAV is replaced, the replaced component is started without authentication. The replaced component can carry out an attack, causing security risks.

SUMMARY

In accordance with the disclosure, there is provided an authentication method including that an authentication apparatus of an unmanned aerial vehicle (UAV) generates a session key, the authentication apparatus receives a device identification (ID) of a device and a randomly generated random number from the device of the UAV, the authentication apparatus obtains a device key of the device according to the device ID of the device, the authentication apparatus encrypts the session key and the random number according to the device key of the device, and the authentication apparatus sends the encrypted session key and the encrypted random number to the device.

Also in accordance with the disclosure, there is provided a secure communication method including that a first device obtains a session key and a command sequence number, the first device generates a message request to communicate with a second device, the first device updates the command sequence number, the first device encrypts the message request and performs message authorization code (MAC) computation on the message request, and the first device sends the encrypted and MAC-computed message request and the updated command sequence number to the second device.

Also in accordance with the disclosure, there is provided a flight controller of an unmanned aerial vehicle (UAV). The flight controller is configured to generate a session key, receive a device ID of a functional assembly of the UAV and a random number, obtain a device key of the functional assembly according to the device ID of the functional assembly, encrypt the session key and the random number according to the device key of the functional assembly, and send the encrypted session key and the encrypted random number to the functional assembly.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of an application environment of an unmanned aerial vehicle (UAV) authentication system according to the disclosure.

FIG. 2 is a schematic diagram of a multi-layered key according to the disclosure.

FIG. 3 is a block diagram of a UAV authentication system according to the disclosure.

FIG. 4 is a flowchart of a UAV authentication method according to the disclosure.

FIG. 5 is a flowchart of another UAV authentication method according to the disclosure.

FIG. 6 is a flowchart of another UAV authentication method according to the disclosure.

FIG. 7 schematically shows an interaction between at least one device and an authentication apparatus according to the disclosure.

FIG. 8 schematically shows a secure communication between two devices according to the disclosure.

DESCRIPTION OF MAIN COMPONENTS AND REFERENCE NUMERALS

-   UAV 1 -   UAV authentication system 10 -   Authentication apparatus 11 -   Device 12 -   Storage apparatus 13 -   Controller 14 -   Generating circuit 100 -   First receiving circuit 101 -   Acquisition circuit 102 -   Encryption circuit 103 -   First sending circuit 104 -   First determination circuit 105 -   Second sending circuit 106 -   Second receiving circuit 107 -   Decryption circuit 108 -   Second determination circuit 109 -   First device 61 -   Second device 62

DETAILED DESCRIPTION OF THE EMBODIMENTS

Technical solutions of the present disclosure will be described with reference to the drawings. It will be appreciated that the described embodiments are some rather than all of the embodiments of the present disclosure. Other embodiments conceived by those having ordinary skills in the art on the basis of the described embodiments without inventive efforts should fall within the scope of the present disclosure.

Exemplary embodiments will be described with reference to the accompanying drawings.

FIG. 1 is a schematic diagram of an application environment of an unmanned aerial vehicle (UAV) authentication system 10 consistent with the disclosure.

As shown in FIG. 1, the UAV authentication system 10 is provided in a UAV 1. The UAV 1 also includes an authentication apparatus 11, at least one device 12, a storage apparatus 13, a controller 14, or the like. The authentication apparatus 11 can include a flight controller of the UAV 1. In some embodiments, the UAV authentication system 10 can be a separate system coupled to the authentication apparatus 11 and the at least one device 12. In some other embodiments, the UAV authentication system 10 can be integrated in the authentication apparatus 11 and the at least one device 12. The authentication apparatus 11, the storage apparatus 13, and the controller 14 can be integrated in the flight controller of the UAV 1. The flight controller (not shown in FIG. 1) of the UAV 1 can be arranged at a fuselage of the UAV 1. The at least one device 12 can include a plurality of components of the UAV 1 or a plurality of functional assemblies of the UAV 1. For example, the plurality of functional assemblies may include one or more of a camera, a gimbal, a remote controller, and a positioning apparatus.

In some embodiments, each of the at least one device 12 corresponds to a unique device identification (ID) that is used for identifying each of the at least one device 12. In some embodiments, the at least one device 12 can be divided into a plurality of groups, for example, a first group of devices, a second group of devices, . . . , an Nth group of devices, or the like. Each group of devices can include at least one functional assembly. For example, the first group of devices can include a camera, camera-associated components and/or similar components, or the like; the second group of devices can include a gimbal, gimbal-associated components and/or similar components, or the like; and the third group of devices can include a remote controller, remote controller-associated components and/or similar components, or the like. Each group of devices corresponds to a device type. Each device type corresponds to a unique device type ID that is used for identifying each group of devices.

FIG. 2 is a schematic diagram of a multi-layered key consistent with the disclosure. The authentication apparatus 11 corresponds to a unique authentication key. Each device type corresponds to a device type key, and each of the at least one device 12 corresponds to a device key. Each device type key can be generated according to the device type ID of the corresponding each device type. The device key of each of the at least one device 12 can be generated, according to the corresponding device ID, the authentication key, and the device type key of the device type to which each of the at least one device 12 belongs. When the authentication apparatus 11 performs communication authentication with each of at least one device 12, a session key can be established.

In some embodiments, there is no need to divide the at least one device 12 into the plurality of groups. The device key of each of the at least one device 12 can be directly generated based on the corresponding device ID and the authentication key.

In some embodiments, the device key of each of the at least one device 12 can be generated by a server during a generating process, according to the above-described processes. After being generated, the device key of each of the at least one device 12 can be pre-programmed in a chip of the UAV 1 and/or be solidified in a firmware of the UAV 1. As such, the security of the UAV 1 can be increased.

In some embodiments, the controller 14 can be configured to implement and process various types of message commands and data of the UAV 1. The storage apparatus 13 can be configured to store various types of data of the UAV 1. In some embodiments, the storage apparatus 13 may be a memory externally connected to the UAV 1 or may be a flash memory.

FIG. 3 is a block diagram of the UAV authentication system 10 consistent with the disclosure. As shown in FIG. 3, the UAV authentication system 10 is divided into one or more circuits. In some embodiments, functions of the one or more circuits can be implemented by one or more software programs stored in the storage apparatus 13 and executed by one or more controllers (such as the controller 14), such that an authentication between the authentication apparatus 11 of the UAV 1 and each of the at least one device 12 described above can be achieved.

As shown in FIG. 3, the UAV authentication system 10 provided at the authentication apparatus 11 includes a generating circuit 100, a first receiving circuit 101, an acquisition circuit 102, an encryption circuit 103, a first sending circuit 104, and a first determination circuit 105. Furthermore, the UAV authentication system 10 provided at one of the at least one device 12 includes a second sending circuit 106, a second receiving circuit 107, a decryption circuit 108, and a second determination circuit 109.

FIG. 4 is a flowchart of a UAV authentication method consistent with the disclosure. FIG. 4 illustrates implementation processes of the UAV authentication system 10 at the authentication apparatus 11.

At S10, when the UAV 1 is powered up or reset, the generating circuit 100 generates a session key for each of the at least one device 12.

In some embodiments, each of the at least one device 12 can provide a randomly generated random number in a plaintext manner and send the device ID and the randomly generated random number to the authentication apparatus 11 in a plaintext manner.

At S11, the first receiving circuit 101 receives the device ID and the random number sent by each of the at least one device 12.

At S12, the acquisition circuit 102 obtains the device key of each of the at least one device 12 according to the device ID of each of the at least one device 12.

In some embodiments, the device key and the device ID of each of the at least one device 12 are stored in the storage apparatus 13. The acquisition circuit 102 can directly read the device key of each of the at least one device 12 from the storage apparatus 13, according to the device ID of each of the at least one device 12. In some embodiments, the acquisition circuit 102 can generate the device key of each of the at least one device 12, according to the device ID of each of the at least one device 12, the authentication key of the authentication apparatus 11, and the device type key of the device type to which each of the at least one device 12 belongs. In some other embodiments, when the at least one device 12 is not divided into the plurality of groups, the acquisition circuit 102 can directly generate the device key of each of the at least one device 12, according to the device ID of each of the at least one device 12 and the authentication key. In some embodiments, the device key is generated in real time.

At S13, the encryption circuit 103 encrypts the session key and the random number, according to the device key of each of the at least one device 12.

In some embodiments, the encryption circuit 103 can use an encryption algorithm for performing encryption. The encryption algorithm may be a Triple Data Encryption Algorithm (TDEA), an Advanced Encryption Standard (AES), or the like. An encryption mode can use Counter (CTR) mode, Galois/Counter Mode (GCM) mode, or another mode.

At S14, the first sending circuit 104 sends the encrypted session key and the encrypted random number to each of the at least one device 12.

In some embodiments, each of the at least one device 12 can decrypt the received encrypted session key and the received encrypted random number based on the device key of each of the at least one device 12. After decryption, each of the at least one device 12 can send a message command to the authentication apparatus 11 using the session key and the device key.

At S15, the first receiving circuit 101 receives the message command sent by each of the at least one device 12.

At S16, the first determination circuit 105 determines whether an authentication of each of the at least one device 12 is passed according to the received message command.

In some embodiments, the first determination circuit 105 may check whether the authentication of each of the at least one device 12 is passed by checking the received message command through a Cyclic Redundancy Check (CRC). The received message command can be checked for each of the at least one device 12. When an error is detected in the received message command, the first determining circuit 105 can determine that corresponding one of the at least one device 12 is not authenticated. When no error is detected in the received message command of each of the at least one device 12, the first determining circuit 105 can determine that each of the at least one device 12 is authenticated.

In some embodiments, the first determination circuit 105 can also determine whether the authentication of each of the at least one device 12 is passed by verifying an integrity of the message command using a Message Digest. The digest generated by the received message command can be compared with the digest generated by the message command sent by each of the at least one device 12. When the digest generated by the received message command is consistent with the digest generated by the message command sent by each of the at least one device 12, the first determination circuit 105 can determine that the authentication of each of the at least one device 12 is passed. When the digest generated by the received message command is inconsistent with the digest generated by the message command sent by each of the at least one device 12, the first determination circuit 105 can determine that the authentication of the at least one device 12 is failed.

In some embodiments, the CRC code and Message Digest can be used at the same time to verify the received message command.

In some other embodiments, the processes at S15 and S16 can be omitted.

FIG. 5 is a flowchart of another UAV authentication method consistent with the disclosure. FIG. 5 illustrates implementation processes of the UAV authentication system 10 at each of the at least one device 12.

At S30, when the UAV 1 is powered up or reset, the authentication apparatus 11 generates a session key for each of the at least one device 12, and each of the second sending circuit 106 sends the device ID of each of the second sending circuit 106 and the randomly generated random number to the authentication apparatus 11 in a plaintext manner.

In some embodiment, the authentication apparatus 11 can encrypt the session key and the random number according to the device key of each of the at least one device 12.

At S31, the second receiving circuit 107 of each of the at least one device 12 receives the encrypted session key and the encrypted random number sent by the authentication apparatus 11.

At S32, the decryption circuit 108 of each of the at least one device 12 decrypts the received encrypted session key and the received encrypted random number according to the device key of each of the at least one device 12.

In some embodiments, the decryption circuit 108 can use an encryption algorithm for encryption. The encryption algorithm may be a Triple Data Encryption Algorithm (TDEA), an Advanced Encryption Standard (AES), or the like.

At S33, the second determination circuit 109 of each of the at least one device 12 determines whether an authentication with the authentication apparatus 11 by each of the at least one device 12 is passed, according to the decrypted random number and the randomly generated random number.

In some embodiments, when the decrypted random number is the same as the randomly generated random number of each of the at least one device 12, the second determination circuit 109 can determine that the authentication with the authentication apparatus 11 by each of the at least one device 12 is passed and the process at S34 can be performed. When the decrypted random number is different from the randomly generated random number of one of the at least one device 12, the second determination circuit 109 can determine that the authentication with the authentication apparatus 11 by one of the at least one device 12 is failed.

At S34, the second sending circuit 106 sends a message command to the authentication apparatus 11.

In some embodiments, the second sending circuit 106 can process the message command, according to the decrypted session key and the device key of each of the at least one device 12 and can send the processed message command to the authentication apparatus 11. The authentication apparatus 11 can verify the integrity and correctness of the received message command using a cyclic redundancy check code and/or a Message Digest.

In some other embodiments, the process at S34 can be omitted.

FIG. 6 is a flowchart of another UAV authentication method consistent with the disclosure. FIG. 7 schematically shows an interaction between the at least one device 12 and the authentication apparatus 11 consistent with the disclosure. FIG. 6 and FIG. 7 illustrate implementation processes of the UAV authentication system 10 at the authentication apparatus 11 and each of the at least one device 12.

At S50, when the UAV 1 is powered up or reset, the generating circuit 100 generates a session key for each of the at least one device 12.

At S51, the second sending circuit 106 sends the device ID of each of the at least one device 12 and the randomly generated random number to the authentication apparatus 11.

At S52, the first receiving circuit 101 receives the device ID and random number sent by each of the at least one device 12.

At S53, the acquisition circuit 102 obtains the device key of each of the at least one device 12, according to the device ID of each of the at least one device 12.

At S54, the encryption circuit 103 encrypts the session key and the random number according to the device key of each of the at least one device 12.

At S55, the first sending circuit 104 sends the encrypted session key and the encrypted random number to each of the at least one device 12.

At S56, the second receiving circuit 107 of each of the at least one device 12 receives the encrypted session key and the encrypted random number sent by the authentication apparatus 11.

At S57, the decryption circuit 108 of each of the at least one device 12 decrypts the received encrypted session key and the received encrypted random number according to the device key of each of the at least one device 12.

At S58, the second determination circuit 109 of each of the at least one device 12 determines whether the authentication with the authentication apparatus 11 by each of the at least one device 12 is passed, according to the decrypted random number and the randomly generated random number.

At S59, when the authentication with the authentication apparatus by each of the at least one device 12 is passed, the second sending circuit 106 of each of the at least one device 12 sends a message command to the authentication apparatus 11, according to the decrypted session key and the device key of each of the at least one device 12.

At S60, the first receiving circuit 101 receives the message command sent by each of the at least one device 12.

At S61, the first determination circuit 105 determines whether the authentication of each of the at least one device 12 is passed, according to the received message command.

In some embodiments, the processes at S59-S61 can be omitted.

In some embodiments, the UAV authentication system 10 can divide the at least one device 12 into at least two groups including a group of necessary devices and a group of unnecessary devices. The UAV authentication system 10 can prohibit the UAV 1 from starting, when at least one of the necessary devices fails to pass the authentication. In some embodiments, when all of the at least one device 12 pass the authentication with the authentication apparatus 11 or when at least one necessary device fails to pass the authentication with the authentication apparatus 11, the UAV authentication system 10 can start the UAV 1.

In some embodiments, if the authentication apparatus 11 loses power during the authentication process between the authentication apparatus 11 and each of the at least one device 12, the authentication apparatus 11 can inform each of the at least one device 12 to perform key exchange again using feedback information (such as by returning a feedback value or by broadcasting). When one of the at least one device 12 loses power during the authentication process between the authentication apparatus 11 and each of the at least one device 12, the one of the at least one device 12 can inform the authentication apparatus 11 to perform key exchange again or to resend the session key using feedback information (such as by returning a feedback value or by broadcasting). In some embodiments, the authentication apparatus 11 can be notified to repower-up and perform key exchange again.

In some embodiments, when generating the session key, the authentication apparatus 11 can generate a command sequence number at the same time, encrypt the session key, the random number, and the command sequence number, according to the device key of each of the at least one device 12, and send the encrypted session key, the encrypted random number, and the encrypted command sequence number to each of the at least one device 12. Each of the at least one device 12 can decrypt the received encrypted session key, the received encrypted random number, and the received encrypted command sequence number. The command sequence number can be automatically sent at a preset time interval (e.g., every 20 ms) or every time a command is sent (e.g., between one of the at least one device 12 and another one of the at least one device 12 or between one of the at least one device 12 and the authentication apparatus 11) and can be automatically incremented by a preset value (e.g., one).

In some embodiments, an initial value of the command sequence number can be zero or another preset value. The command sequence number can be automatically incremented each time the command is sent or can be automatically incremented according to the above preset time interval.

In some embodiments, the generated session key and the generated command sequence number can be stored in the storage apparatus 13 or an external storage apparatus for protection. When the authentication apparatus 11 undergoes a warm restart during the authentication process, each of the at least one device 12 can directly read the session key and the command sequence number from the storage apparatus 13 and the process of rekey exchange can be omitted. The command sequence number can be configured to determine whether the message command sent by one of the at least one device 12 or the authentication apparatus 11 to another one of the at least one device 12 is an expired command. When the message command is an expired command, the another one of the at least one device 12 will not respond to the received message command, which will be described in detailed in FIG. 8.

In some embodiments, the flight controller of the UAV 1 can be configured to generate a session key for each functional assembly. Each functional assembly, i.e., each of the above-described at least one device 12, such as a camera, a gimbal, a remote controller, or the like, can be configured to send the device ID of each functional assembly and the randomly generated random number to the flight controller. The flight controller can obtain the device key of each functional assembly according to the device ID, encrypt the session key and the random number according to the device key of each functional assembly, and send the encrypted session key and the encrypted random number to each functional assembly. Each functional assembly can decrypt the received encrypted session key and the received encrypted random number according to the device key of each functional assembly, and determine whether the authentication of the flight controller is passed according to the decrypted random numbers and the decrypted randomly generated random numbers.

FIG. 8 schematically shows a secure communication between two devices consistent with the disclosure. As shown in FIG. 8, a first device 61 is to establish a communication connection with a second device 62. The first device 61 obtains the session key and the command sequence number. In some embodiment, the first device 61 receives the encrypted session key, the encrypted random number, and the command sequence number sent by the authentication apparatus 11 during the authentication process with the authentication apparatus 11. The first device 61 generates a message request to communicate with the second device 62. The first device 61 updates the acquired command sequence number. The first device 61 uses the session key to encrypt the message request and perform message authorization code (MAC) computation on the message request. The first device 61 sends the encrypted and MAC-computed message request and the updated command sequence number to the second device 62.

In some embodiments, the session key can include an encryption key and a MAC key correspond to the encryption and the MAC computation, respectively. In some embodiments, the session key can include only one of the encryption key and the MAC key. In some other embodiments, the session key can also include a plurality of other types of session keys in addition to the encryption key and the MAC key.

The second device 62 receives a MAC, the encrypted message request, and the updated command sequence number sent by the first device 61. When the received command sequence number is greater than the command sequence number stored in the storage apparatus of the second device 62, the second device 62 updates the stored command sequence number. The second device 62 decrypts the encrypted message request using the session key. The second device 62 verifies the received MAC. When a verification of the received MAC is passed, the second device 62 generates a response message based on the decrypted message request. The second device 62 generates another MAC based on the received command sequence number, the received session key, and the response message. The second device 62 encrypts the response message using the session key. The second device 62 sends the another MAC, the encrypted response message, and the received command sequence number to the first device 61.

When the received command sequence number is less than or equal to the command sequence number stored in the storage apparatus of the second device 62, it indicates that the message request sent by the first device 61 to the second device 62 has been processed and is an expired command. As such, replay attacks can be effectively prevented.

The first device 61 can receive the another MAC generated based on the received command sequence number, the session key, and the response message, the encrypted response message, and the command sequence number sent by the second device 62. The first device 61 can verify the received MAC. When the verification of the MAC is passed, the first device 61 can decrypt the received encrypted response message.

It is intended that the specification and examples be considered as exemplary only and not to limit the scope of the disclosure. Those skilled in the art will be appreciated that any modification or equivalents to the disclosed embodiments are intended to be encompassed within the scope of the present disclosure. 

What is claimed is:
 1. An authentication method comprising: sending, by a device of an unmanned aerial vehicle (UAV), a device identification (ID) of the device and a randomly generated random number to an authentication apparatus of the UAV; receiving, by the device from the authentication apparatus, an encrypted session key and an encrypted random number that are obtained by the authentication apparatus based on the device identification; decrypting, by the device according to a device key of the device, the encrypted session key and the encrypted random number to obtain decrypted session key and decrypted random number, respectively; and determining, by the device, whether an authentication of the authentication apparatus is passed based on the randomly generated random number and the decrypted random number.
 2. The method of claim 1, further comprising: sending, by the device, a message command to the authentication apparatus in response to determining that the authentication of the authentication apparatus is passed.
 3. The method of claim 2, further comprising: generating, by the device, the message command using the decrypted session key and the device key.
 4. The method of claim 1, wherein the device key is generated based on at least the device ID of the device.
 5. The method of claim 4, wherein the device key is generated based on the device ID of the device and an authentication key of the authentication apparatus.
 6. The method of claim 5, wherein: the device belongs to one of a plurality of groups of devices; and each of the plurality of groups of devices corresponds to a device type having a device type ID identifying the device type.
 7. The method of claim 6, wherein the device key is generated based on the device ID of the device, the authentication key of the authentication apparatus, and a device type key of a device type corresponding to the one of the plurality of groups of devices to which the device belongs.
 8. The method of claim 4, wherein the device key is generated in real time.
 9. The method of claim 1, wherein the device key is pre-programmed in a storage chip of the UAV and/or solidified in firmware of the UAV.
 10. The method of claim 1, wherein determining whether an authentication of the authentication apparatus is passed based on the randomly generated random number and the decrypted random number includes: determining that the authentication of the authentication apparatus is passed in response to the decrypted random number being consistent with the randomly generated random number; and determining that the authentication with the authentication apparatus is failed in response to the decrypted random number being inconsistent with the randomly generated random number.
 11. The method of claim 1, further comprising: receiving, from the authentication apparatus, an encrypted command sequence number that is obtained by the authentication apparatus encrypting a command sequence number according to the device key of the device, the command sequence number being generated by the authentication apparatus when a session key corresponding to the encrypted session key is generated; and decrypting the encrypted command sequence number to obtain decrypted command sequence number.
 12. The method of claim 11, wherein: the command sequence number is automatically incremented by a preset value at a preset time interval or every time a command is sent.
 13. The method of claim 1, wherein: the encrypted session key is obtained by the authentication apparatus by encrypting a session key, the session key being generated by the authentication apparatus for the device in response to the UAV being powered up or reset.
 14. The method of claim 1, wherein sending the device ID of the device and the randomly generated random number to the authentication apparatus of the UAV includes: sending the device ID of the device and the randomly generated random number to the authentication apparatus of the UAV in a plaintext manner.
 15. An functional assembly of an unmanned aerial vehicle (UAV), the functional assembly being configured to: send a device identification (ID) of the functional assembly and a randomly generated random number to a flight controller of the UAV; receiving, by the functional assembly from the flight controller, an encrypted session key and an encrypted random number that are obtained by the flight controller based on the device identification; decrypt, according to a device key of the functional assembly, the encrypted session key and the encrypted random number to obtain decrypted session key and decrypted random number, respectively; and determine whether an authentication of the flight controller is passed based on the randomly generated random number and the decrypted random number.
 16. An unmanned aerial vehicle (UAV), comprising: a flight controller; and a functional assembly coupled to the flight controller, the functional assembly being configured to: send a device identification (ID) of the functional assembly and a randomly generated random number to the flight controller; receive, from the flight controller, an encrypted session key and an encrypted random number that are obtained by the flight controller based on the device identification; decrypt, according to a device key of the functional assembly, the encrypted session key and the encrypted random number to obtain decrypted session key and decrypted random number, respectively; and determine whether an authentication of the flight controller is passed based on the randomly generated random number and the decrypted random number.
 17. The UAV of claim 16, wherein the functional assembly is further configured to: send a message command to the flight controller in response to determining that the authentication of the flight controller is passed.
 18. The UAV of claim 17, wherein the functional assembly is further configured to: generate the message command using the decrypted session key and the device key.
 19. The UAV of claim 16, wherein the functional assembly is further configured to: determine that the authentication of the flight controller is passed in response to the decrypted random number being consistent with the randomly generated random number; and determine that the authentication with the flight controller is failed in response to the decrypted random number being inconsistent with the randomly generated random number.
 20. The UAV of claim 16, wherein the functional assembly is further configured to: receive, from the flight controller, an encrypted command sequence number that is obtained by the flight controller encrypting a command sequence number according to the device key of the functional assembly, the command sequence number being generated by the flight controller when a session key corresponding to the encrypted session key is generated; and decrypt the encrypted command sequence number to obtain decrypted command sequence number. 